fix(memory): show a write in the wiki and the vault mount right away - #69
Merged
Conversation
A committed page only became visible once the curator's next poll tick
projected it, so an agent could tick an item off, read the page back to
check itself, and find its own work missing.
Every write now asks the curator to project it and waits briefly. The
curator stays the projection's only writer: writers ask, they never
mirror. A projection that has not caught up in time is reported as a
delay ("the wiki and the vault mount catch up shortly"), never as a
failed write.
With the AI endpoint down, the curator retried the same rebuild on every quiet window, indefinitely, printing a line each time that looked like a healthy heartbeat. Observed running for hours. The gap now doubles with each consecutive failure up to an hour, and the log says how many attempts failed and when the next one is due. Source mirroring is untouched: it stays undebounced, so the wiki and the vault mount keep receiving new pages while generation is down.
Contributor
Author
|
Verified on the demo rig with all changes live after 2.2s from The lag path fired on its own when a later write landed mid-rebuild (a real rebuild took 2m14s), printing: Commit reported as done, delay reported as a delay. Side finding: the Quartz chokidar watcher does fire across the macOS bind mount, so no Full non-integration suite: 2437 passed, 8 skipped, 0 failed. ruff clean. Not built, worth follow-ups:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A committed page was only visible once the curator's next poll tick projected it, so an agent could tick an item off, read the page back, and find its own work missing.
Writes now ask the curator to project them and wait briefly. The curator stays the projection's only writer (ADR-011): writers ask, they never mirror. A projection that has not caught up in time reports as a delay, never a failed write.
Also bounds the curator's failed-rebuild retry: the window doubles per consecutive failure up to an hour, and the log says how many attempts failed and when the next is due.